Skip to content

docs: replace README template with OrgExplorer content and fix links#43

Open
kunal-bunkar wants to merge 1 commit intoAOSSIE-Org:mainfrom
kunal-bunkar:docs/improve-readme
Open

docs: replace README template with OrgExplorer content and fix links#43
kunal-bunkar wants to merge 1 commit intoAOSSIE-Org:mainfrom
kunal-bunkar:docs/improve-readme

Conversation

@kunal-bunkar
Copy link

@kunal-bunkar kunal-bunkar commented Mar 16, 2026

Addressed Issues:

Fixes #39

Documentation-only change. No UI or runtime changes. README now reflects OrgExplorer’s purpose, features, and setup.

Additional Notes:

  • README: Replaced all TODO placeholders with OrgExplorer-specific content from the GSoC 2026 project guide.
  • Links: Updated badge and repo links from TODO / AOSSIE-Org/TODO to AOSSIE-Org/OrgExplorer; removed Stability Nexus URLs (Telegram, Medium, YouTube).
  • Content: Added real project description, feature list (health score, inactive repos, contributor ranking, heatmaps, dashboard, etc.), and actual tech stack (React, TypeScript, Vite, GitHub API, IndexedDB, localStorage).
  • Getting Started: Fixed broken emoji (�🍀 → 🚀), correct clone URL, Node 18+ and npm/yarn/pnpm prerequisites, optional VITE_GITHUB_TOKEN env var, and Vite dev server URL (localhost:5173). Documented build, preview, and lint scripts.
  • Assets: Second logo now uses org-explorer-logo.svg with proper alt text. Kept AOSSIE social links (X, Discord, LinkedIn).
  • Cleanup: Removed generic checklist (protocol/smart contracts/mobile/AI) and empty architecture/user-flow placeholders; contributors image points to AOSSIE-Org/OrgExplorer.

Checklist

  • My code follows the project's code style and conventions
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings or errors
  • I have joined the Discord server and I will share a link to this PR with the project maintainers there
  • I have read the Contributing Guidelines

Summary by CodeRabbit

  • Documentation
    • Rebranded project to OrgExplorer across all documentation and references.
    • Updated project description with concrete feature set (health scores, analytics dashboards, contributor rankings).
    • Simplified tech stack information and modernized installation instructions.
    • Clarified that the application runs entirely in the browser with no backend server.
    • Updated getting started guide and contribution guidelines.

@github-actions github-actions bot added configuration documentation Improvements or additions to documentation enhancement New feature or request first-time-contributor javascript size/M size/L and removed size/M labels Mar 16, 2026
@coderabbitai
Copy link

coderabbitai bot commented Mar 16, 2026

Walkthrough

README.md is updated to rebrand the project from TODO to OrgExplorer, including new project description, feature set, tech stack details, installation instructions, and contributor information aligned with the current project scope.

Changes

Cohort / File(s) Summary
Documentation Rebranding
README.md
Complete README refresh: updated project title, description, and branding from TODO to OrgExplorer; replaced placeholder features with concrete feature list (health score, inactivity detection, contributor ranking, heatmaps, dashboards, repo comparison, language breakdown); simplified tech stack to React/TypeScript/Vite with GitHub REST API and IndexedDB; revised Getting Started with modern Vite-based setup instructions and npm/yarn/pnpm commands; updated contributor/maintainer sections and footer badges.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

Documentation

Suggested reviewers

  • Zahnentferner

Poem

🐰 The README hops anew,
From TODO's faded hue,
To OrgExplorer bright and true,
With features fresh and dashboards too! ✨
Our little app now shines right through! 🌟

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: replace README template with OrgExplorer content and fix links' accurately describes the main change - comprehensive README documentation replacement from template placeholders to OrgExplorer-specific content with updated links.
Linked Issues check ✅ Passed The PR fully addresses linked issue #39 requirements: removes placeholder template content, replaces with concrete OrgExplorer information (features, tech stack, setup), updates documentation links/badges, and generates no new warnings or errors.
Out of Scope Changes check ✅ Passed All changes are directly aligned with the linked issue #39 scope: README documentation updates, branding changes from TODO to OrgExplorer, and link fixes. No unrelated code modifications or out-of-scope changes are present.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

CodeRabbit can use Trivy to scan for security misconfigurations and secrets in Infrastructure as Code files.

Add a .trivyignore file to your project to customize which findings Trivy reports.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Line 171: Update the footer copyright in README.md where the line contains "©
2025 AOSSIE" so it reflects the current year (change to "© 2026 AOSSIE" or use a
range like "© 2025–2026 AOSSIE"); locate the exact string "© 2025 AOSSIE" and
replace it accordingly.
- Around line 66-72: Add a blank line immediately after the "### Frontend" and
"### Data & storage" markdown headings to satisfy markdownlint rule MD022;
locate the two heading lines (the literal "### Frontend" and "### Data &
storage") and insert a single blank line following each so the lists/paragraphs
beneath are separated from their subheadings.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: b0d261d4-532b-46ba-ba9f-658a1278b990

📥 Commits

Reviewing files that changed from the base of the PR and between 1cfc3e7 and 9b5d0ad.

📒 Files selected for processing (1)
  • README.md

Comment on lines 66 to +72
### Frontend
- React / Next.js / Flutter / React Native
- TypeScript
- TailwindCSS

### Backend
- Flask / FastAPI / Node.js / Supabase
- Database: PostgreSQL / SQLite / MongoDB

### AI/ML (if applicable)
- LangChain / LangGraph / LlamaIndex
- Google Gemini / OpenAI / Anthropic Claude
- Vector Database: Weaviate / Pinecone / Chroma
- RAG / Prompt Engineering / Agent Frameworks

### Blockchain (if applicable)
- Solidity / solana / cardano / ergo Smart Contracts
- Hardhat / Truffle / foundry
- Web3.js / Ethers.js / Wagmi
- OpenZeppelin / alchemy / Infura
- **React** (with React Router)
- **TypeScript**
- **Vite** (build tooling)

---
### Data & storage
- **GitHub REST API** — Fetched from the browser (no backend).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Add blank lines below subheadings to satisfy markdownlint.

### Frontend and ### Data & storage should each be followed by a blank line (Line 66 and Line 71) to resolve MD022.

Suggested fix
 ### Frontend
+
 - **React** (with React Router)
 - **TypeScript**
 - **Vite** (build tooling)
 
 ### Data & storage
+
 - **GitHub REST API** — Fetched from the browser (no backend).
 - **IndexedDB** — Cache for repos, contributors, commits, issues.
 - **localStorage** — Last org name, theme, preferences.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### Frontend
- React / Next.js / Flutter / React Native
- TypeScript
- TailwindCSS
### Backend
- Flask / FastAPI / Node.js / Supabase
- Database: PostgreSQL / SQLite / MongoDB
### AI/ML (if applicable)
- LangChain / LangGraph / LlamaIndex
- Google Gemini / OpenAI / Anthropic Claude
- Vector Database: Weaviate / Pinecone / Chroma
- RAG / Prompt Engineering / Agent Frameworks
### Blockchain (if applicable)
- Solidity / solana / cardano / ergo Smart Contracts
- Hardhat / Truffle / foundry
- Web3.js / Ethers.js / Wagmi
- OpenZeppelin / alchemy / Infura
- **React** (with React Router)
- **TypeScript**
- **Vite** (build tooling)
---
### Data & storage
- **GitHub REST API** — Fetched from the browser (no backend).
### Frontend
- **React** (with React Router)
- **TypeScript**
- **Vite** (build tooling)
### Data & storage
- **GitHub REST API** — Fetched from the browser (no backend).
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)

[warning] 66-66: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


[warning] 71-71: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 66 - 72, Add a blank line immediately after the "###
Frontend" and "### Data & storage" markdown headings to satisfy markdownlint
rule MD022; locate the two heading lines (the literal "### Frontend" and "###
Data & storage") and insert a single blank line following each so the
lists/paragraphs beneath are separated from their subheadings.

[![Contributors](https://contrib.rocks/image?repo=AOSSIE-Org/OrgExplorer)](https://github.com/AOSSIE-Org/OrgExplorer/graphs/contributors)

© 2025 AOSSIE
© 2025 AOSSIE
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Update the footer year to match the current year.

Line 171 still says © 2025 AOSSIE; this is now stale in 2026 and should be updated (or changed to a range like 2025–2026).

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 171, Update the footer copyright in README.md where the
line contains "© 2025 AOSSIE" so it reflects the current year (change to "© 2026
AOSSIE" or use a range like "© 2025–2026 AOSSIE"); locate the exact string "©
2025 AOSSIE" and replace it accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

configuration documentation Improvements or additions to documentation enhancement New feature or request first-time-contributor javascript size/L

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant